Skip to content

feat(api): add security_boundary field to Cell and MinimalNode schemas#111

Merged
ericfitz merged 1 commit intomainfrom
feature/security-boundary-field
Jan 23, 2026
Merged

feat(api): add security_boundary field to Cell and MinimalNode schemas#111
ericfitz merged 1 commit intomainfrom
feature/security-boundary-field

Conversation

@ericfitz
Copy link
Owner

Summary

  • Add optional security_boundary boolean property to Cell.data schema
  • Add required security_boundary field to MinimalNode schema for WebSocket collaboration
  • Implement shape-based enforcement in transformNodeToMinimal():
    • security-boundary shape → always true
    • text-box shape → always false
    • Other shapes → use data value or default false
  • Include security_boundary in GraphML export

Test plan

  • OpenAPI validation passes
  • Lint passes (0 issues)
  • Build succeeds
  • Unit tests pass

🤖 Generated with Claude Code

Add optional boolean security_boundary property to indicate whether a
node represents a security boundary in threat model diagrams.

- Add security_boundary to Cell.data.properties in OpenAPI spec
- Add security_boundary as required top-level property in MinimalNode
- Update transformNodeToMinimal() with shape-based enforcement rules:
  - security-boundary shape: always true
  - text-box shape: always false
  - other shapes: use data value or default false
- Include security_boundary in GraphML export

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@dosubot dosubot bot added the enhancement New feature or request label Jan 23, 2026
@ericfitz ericfitz merged commit 91af483 into main Jan 23, 2026
7 checks passed
@ericfitz ericfitz deleted the feature/security-boundary-field branch January 23, 2026 02:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant